Method and system for signaling release cause indication in a umts network

ABSTRACT

A method and system for processing signaling release indication cause between user equipment and a wireless network, the method comprising the steps of: monitoring, at the user equipment, whether a signaling connection release indication should be sent to the wireless network; appending, at the user equipment, a cause for the signaling connection release indication to the signaling connection release indication; sending the appended signaling connection release indication to the wireless network; receiving the signaling connection release indication at the wireless network; and filtering said cause to determine whether to raise an alarm.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application claims priority to U.S. Provisional PatentApplication No. 60/747,466, filed May 17, 2006, and also is related toU.S. patent application Ser. No. 11/302,263, filed on Dec. 14, 2005, thecontents of which are incorporated herein by reference in theirentireties.

FIELD OF THE APPLICATION

The present application relates to radio resource control between UserEquipment (UE) and Universal Terrestrial Radio Access Network (UTRAN),and in particular to the release of an existing signaling connection ina UMTS network.

BACKGROUND

A Universal Mobile Telecommunication System (UMTS) is a broadband,packet based system for the transmission of text, digitized voice, videoand multi-media. It is a highly subscribed to standard for thirdgeneration and is generally based on Wideband Coded Division MultipleAccess (W-CDMA).

In a UMTS network, a Radio Resource Control (RRC) part of the protocolstack is responsible for the assignment, configuration and release ofradio resources between the UE and the UTRAN. This RRC protocol isdescribed in detail in the 3GPP TS 25.331 specifications. Two basicmodes that the UE can be in are defined as “idle mode” and “UTRAconnected mode”. UTRA stands for UMTS Terrestrial Radio Access. In idlemode, the UE is required to request a RRC connection whenever it wantsto send any user data or in response to a page whenever the UTRAN or theServing GPRS Support Node (SGSN) pages it to receive data from anexternal data network such as a push server. Idle and Connected modebehaviors are described in details in 3GPP specifications TS 25.304 andTS 25.331.

When in a UTRA RRC connected mode, the device can be in one of fourstates. These are:

-   CELL-DCH: A dedicated channel is allocated to the UE in uplink and    downlink in this state to exchange data. The UE must perform actions    as outlined in 3GPP 25.331.-   CELL_FACH: no dedicated channel is allocated to the user equipment    in this state. Instead, common channels are used to exchange a small    amount of bursty data. The UE must perform actions as outlined in    3GPP 25.331 which includes the cell selection process as defined in    3GPP TS 25.304.-   CELL_PCH: the UE uses Discontinuous Reception (DRX) to monitor    broadcast messages and pages via a Paging Indicator Channel (PICH).    No uplink activity is possible. The UE must perform actions as    outlined in 3GPP 25.331 which includes the cell selection process as    defined in 3GPP TS 25.304. The UE must perform the CELL UPDATE    procedure after cell reselection.-   URA_PCH: the UE uses Discontinuous Reception (DRX) to monitor    broadcast messages and pages via a Paging Indicator Channel (PICH).    No uplink activity is possible. The UE must perform actions as    outlined in 3GPP 25.331 including the cell selection process as    defined in 3GPP TS 25.304. This state is similar to CELL_PCH, except    that URA UPDATE procedure is only triggered via UTRAN Registration    Area (URA) reselection.

The transition from an idle to the connected mode and vise-versa iscontrolled by the UTRAN. When an idle mode UE requests an RRCconnection, the network decides whether to move the UE to the CELL_DCHor CELL_FACH state. When the UE is in an RRC connected mode, again it isthe network that decides when to release the RRC connection. The networkmay also move the UE from one RRC state to another prior to releasingthe connection or in some cases instead of releasing the connection. Thestate transitions are typically triggered by data activity or inactivitybetween the UE and network. Since the network may not know when the UEhas completed data exchange for a given application, it typically keepsthe RRC connection for some time in anticipation of more data to/fromthe UE. This is typically done to reduce the latency of call set-up andsubsequent radio bearer setup. The RRC connection release message canonly be sent by the UTRAN. This message releases the signal linkconnection and all radio bearers between the UE and the UTRAN.

The problem with the above is that even if an application on the UE hascompleted its data transaction and is not expecting any further dataexchange, it still waits for the network to move it to the correctstate. The network may not be even aware of the fact that theapplication on the UE has completed its data exchange. For example, anapplication on the UE may use its own acknowledgement-based protocol toexchange data with its application server which is connected to the UMTScore network. Examples are applications that run over UDP/IPimplementing their own guaranteed delivery. In such a case, the UE knowswhether the application server has sent or received all the data packetsor not and is in a better position to determine if any further dataexchange is to take place and hence decide when to terminate the RRCconnection associated with Packet Service (PS) domain. Since the UTRANcontrols when the RRC connected state is changed to a different state orinto an idle mode, and the fact that UTRAN is not aware of the status ofdata delivery between the UE and external server, the UE is forced tostay in a higher data rate and intensive battery state than the requiredstate or mode, thereby draining battery life. This also results inwasting network resources due to the fact the radio bearer resources areunnecessarily kept occupied.

One solution to the above is to have the UE send a signaling releaseindication to the UTRAN when the UE realizes that it is finished withdata transaction. Pursuant to section 8.1.14.3 of the 3GPP TS 25.331specification, the UTRAN may release the signaling connection uponreceipt of the signaling release indication from the UE, causing the UEto transition to an idle mode. A problem with the above is that thesignaling release indication may be considered an alarm. A networktypically only expects the signaling release indication when a GMMservice request failure, a RAU failure, or a attach failure occur. Theraising of an alarm when the UE request signaling release results ininefficient performance monitoring and alarm monitoring at the network.

BRIEF DESCRIPTION OF THE DRAWINGS

The present application will be better understood with reference to thedrawings in which:

FIG. 1 is a block diagram showing RRC states and transitions;

FIG. 2 is a schematic of a UMTS network showing various UMTS cells and aURA;

FIG. 3 is a block diagram showing the various stages in an RRCconnection setup;

FIG. 4A is a block diagram of an exemplary transition between a CELL_DCHconnected mode state and an idle mode initiated by the UTRAN accordingto current method;

FIG. 4B is a block diagram showing an exemplary transition between aCELL_DCH state connected mode transition to an idle mode utilizingsignaling release indications;

FIG. 5A is a block diagram of an exemplary transition between a CELL_DCHinactivity to a CELL_FACH inactivity to an idle mode initiated by theUTRAN;

FIG. 5B is a block diagram of an exemplary transition between CELL_DCHinactivity and an idle mode utilizing signaling release indications;

FIG. 6 is a block diagram of a UMTS protocol stack;

FIG. 7 is an exemplary UE that can be used in association with thepresent method;

FIG. 8 is an exemplary network for use in association with the presentmethod and system;

FIG. 9 is a flow diagram showing the steps of adding a cause for asignaling connection release indication at the UE; and

FIG. 10 is a flow diagram showing the steps taken by a UE upon receiptof a signaling connection release indication having a cause.

DETAILED DESCRIPTION

The present system and method provide for the transitioning from an RRCconnected mode to a more battery efficient state or mode while ensuringthe network does not consider a signaling release indication to be analarm if the cause of the signaling release indication is a UE idletransition request. In particular, the present method and apparatusprovide for transitioning based on either the UE initiating terminationof a signaling connection for a specified core network domain orindicating to the UTRAN that a transition should occur from oneconnected state to another. The following description shall be describedwith respect to the exemplary implementation of a UMTS. It should beunderstood, however, that the teachings of the present invention areanalogously applicable to other radio communication systems.

In particular, if an application on the UE determines that it is donewith the exchange of data, it can send a “done” indication to the “RRCconnection manager” component of UE software. The RRC connection managerkeeps track of all existing applications (including those providing aservice over one or multiple protocols), associated Packet Data Protocol(PDP) contexts, associated packet switched (PS) radio bearers andassociated circuit switched (CS) radio bearers. A PDP Context is alogical association between a UL and PDN (Public Data Network) runningacross a UMTS core network. One or multiple applications (e.g. an e-mailapplication and a browser application) on the UE may be associated withone PDP context. In some cases, one application on the UE is associatedwith one primary PDP context and multiple applications may be tied withsecondary PDP contexts. The RRC Connection Manager receives “done”indications from different applications on the UE that aresimultaneously active. For example, user may receive an e-mail from apush server while browsing the web. After the e-mail application hassent an acknowledgment, it may indicate that it has completed its datatransaction, however, the browser application may not send suchindication. Based on a composite status of such indications from activeapplications, UE software can decide how long it should wait before itcan initiate a signaling connection release of the core network packetservice domain. A delay in this case can be introduced to ensure thatthe application is truly finished with data exchange and does notrequire an RRC connection. The delay can be dynamic based on traffichistory and/or application profiles. Whenever the RRC connection managerdetermines that with some probability that no application is expected toexchange any data, it can send a signaling connection release indicationprocedure for the appropriate domain (e.g. PS domain). Alternatively itcan send a request for state transition within connected mode to theUTRAN.

The above decision may also take into account whether network supportsURA_PCH state and the transition behavior to this state.

The UE initiated transition to idle mode can happen from any state ofthe RRC connected mode and ends up having the network release the RRCconnection and moving to idle mode. The UE being in idle mode, as willbe appreciated by those skilled in the art, is much less batteryintensive than the UE being in a connected state.

The sending of the signaling release indication however can cause thenetwork to consider that an alarm has occurred. In the case that thesignaling release indication is a result of the RRC determining that notraffic is expected, in a preferred embodiment the network candistinguish the fact that the signaling release indication is a resultof a requested idle transition as opposed to an abnormal condition. Thisdistinction allows indicators such as the Key Performance Indicator(KPI) to be more accurate, thereby improving performance monitoring andalarm monitoring.

The present method allows the UE to append, to an existing signalingrelease indication, a field providing the cause for the signalingrelease indication. The network may then use the appended field tofilter true alarm conditions from situations in which a UE has requestedto be put into an idle state because it is expecting no further data.This improves the efficiency of alarm and performance monitoring, whilestill allowing the UE to save battery resources by moving into an idlemode more quickly.

The present application therefore provides a method for processingsignaling release indication cause between user equipment and a wirelessnetwork, comprising the steps of: monitoring, at the user equipment,whether a signaling connection release indication should be sent to thewireless network; appending, at the user equipment, a cause for thesignaling connection release indication to the signaling connectionrelease indication; sending the appended signaling connection releaseindication to the wireless network; receiving the signaling connectionrelease indication at the wireless network; and filtering said cause todetermine whether to raise an alarm

The present application further provides a system adapted for processingsignaling release indication cause, the system comprising: userequipment, the user equipment having a radio subsystem including a radioadapted to communicate with the UMTS network; a radio processor having adigital signal processor and adapted to interact with said radiosubsystem; memory; a user interface; a processor adapted to run userapplications and interact with the memory, the radio and the userinterface and adapted to run applications, the user equipmentcharacterized by having means for: monitoring whether a signalingconnection release indication should be sent to the wireless network;appending a cause for the signaling connection release indication to thesignaling connection release indication; and sending the appendedsignaling connection release indication to the wireless network; and awireless network adapted to communicate with the user equipment andfurther characterized by means for: receiving the signaling connectionrelease indication; and filtering said cause to determine whether toraise an alarm.

The present application still further provides a method for processingsignaling release indication cause at user equipment for improved alarmtracking at a wireless network, comprising the steps of: monitoringwhether a signaling connection release indication should be sent to thewireless network; appending a cause for the signaling connection releaseindication to the signaling connection release indication; and sendingthe appended signaling connection release indication to the wirelessnetwork, wherein said wireless network is provided with an indication ofthe cause of the signaling connection release indication.

The present application still further provides apparatus for userequipment to facilitate release of a signaling connection. A checker isconfigured to check whether a signaling connection release indicationshould be sent. A signaling connection release indication sender isconfigured to send a signaling connection release indication responsiveto indication by the checker that the signaling connection releaseindication by the checker that the signaling connection releaseindication should be sent. The signaling connection release indicationincludes a signaling release indication cause field.

The present application still further provides network apparatus foroperating upon a signaling connection release indication. An examiner isconfigured to examine a signaling release indication cause field of thesignaling connection release indication. The examiner checks whether thesignaling release indication cause field indicates an abnormalcondition. An alarm generator is configured selectably to generate analarm if examination by the examiner determines that the signalingrelease indication cause field indicates the abnormal condition.

The present application yet further provides a user equipment adaptedfor providing signaling release indication cause in a UMTS network, theuser equipment having a radio subsystem including a radio adapted tocommunicate with the UMTS network; a radio processor having a digitalsignal processor and adapted to interact with said radio subsystem;memory; a user interface; a processor adapted to run user applicationsand interact with the memory, the radio and the user interface andadapted to run applications, the user equipment characterized by havingmeans for: monitoring whether a signaling connection release indicationshould be sent to the wireless network; appending a cause for thesignaling connection release indication to the signaling connectionrelease indication; and sending the appended signaling connectionrelease indication to the wireless network, wherein said wirelessnetwork is provided with an indication of the cause of the signalingconnection release indication.

Reference is now made to FIG. 1. FIG. 1 is a block diagram showing thevarious modes and states for the radio resource control portion of aprotocol stack in a UMTS network. In particular, the RRC can be eitherin an RRC idle state 110 or an RRC connected state 120.

As will be appreciated by those skilled in the art, a UMTS networkconsists of two land-based network segments. These are the Core Network(CN) and the Universal Terrestrial Radio-Access Network (UTRAN) (asillustrated in FIG. 8). The Core Network is responsible for theswitching and routing of data calls and data connections to the externalnetworks while the UTRAN handles all radio related functionalities.

In idle mode 110, the UE must request an RRC connection to set up theradio resource whenever data needs to be exchanged between the UE andthe network. This can be as a result of either an application on the UErequiring a connection to send data, or as a result of the UE monitoringa paging channel to indicate whether the UTRAN or SGSN has paged the UEto receive data from an external data network such as a push server. Inaddition, UE also requests RRC connection whenever it needs to sendMobility Management signaling messages such as Location Area Update.

Once the UE has sent a request to the UTRAN to establish a radioconnection, the UTRAN chooses a state for the RRC connection to be in.Specifically, the RRC connected mode 120 includes four separate states.These are CELL_DCH state 122, CELL_FACH state 124, CELL_PCH state 126and URA_PCH state 128.

From idle mode 110 the RRC connected state can either go to the CellDedicated Channel (CELL_DCH) state 122 or the Cell Forward AccessChannel (CELL_FACH) state 124.

In CELL_DCH state 122, a dedicated channel is allocated to the UE forboth uplink and downlink to exchange data. This state, since it has adedicated physical channel allocated to the UE, typically requires themost battery power from the UE.

Alternatively, the UTRAN can move from idle mode 110 to a CELL_FACHstate 124. In a CELL_FACH state no dedicated channel is allocated to theUE. Instead, common channels are used to send signaling in a smallamount of bursty data. However, the UE still has to continuously monitorthe FACH, and therefore it consumes battery power.

Within the RRC connected mode 120, the RRC state can be changed at thediscretion of the UTRAN. Specifically, if data inactivity is detectedfor a specific amount of time or data throughput below a certainthreshold is detected, the UTRAN may move the RRC state from CELL_DCHstate 122 to the CELL_FACH state 124, CELL_PCH state 126 or URA_PCHstate 128. Similarly, if the payload is detected to be above a certainthreshold then the RRC state can be moved from CELL_FACH 124 to CELL_DCH122.

From CELL_FACH state 124, if data inactivity is detected forpredetermined time in some networks, the UTRAN can move the RRC statefrom CELL_FACH state 124 to a paging channel (PCH) state. This can beeither the CELL_PCH state 126 or URA_PCH state 128.

From CELL_PCH state 126 or URA_PCH state 128 the UE must move toCELL_FACH state 124 in order to initiate an update procedure to requesta dedicated channel. This is the only state transition that the UEcontrols.

CELL_PCH state 126 and URA_PCH state 128 use a discontinuous receptioncycle (DRX) to monitor broadcast messages and pages by a PagingIndicator Channel (PICH). No uplink activity is possible.

The difference between CELL_PCH state 126 and URA_PCH state 128 is thatthe URA_PCH state only triggers a URA Update procedure if the UEscurrent UTRAN registration area (URA) is not among the list of URAidentities present in the current cell. Specifically, reference is madeto FIG. 2. FIG. 2 shows an illustration of various UMTS cells 210, 212and 214. All of these cells require a cell update procedure ifreselected to a CELL_PCH state. However, in a UTRAN registration area,each will be within the same UTRAN registration area 220, and thus a URAupdate procedure is not triggered when moving between 210, 212 and 214when in a URA_PCH mode.

As seen in FIG. 2, other cells 218 are outside the URA 220, and can bepart of a separate URA or no URA.

As will be appreciated by those skilled in the art, from a battery lifeperspective the idle state provides the lowest battery usage comparedwith the states above. Specifically, because the UE is required tomonitor the paging channel only at intervals, the radio does not need tocontinuously be on, but will instead wake up periodically. The trade-offfor this is the latency to send data. However, if this latency is nottoo great, the advantages of being in the idle mode and saving batterypower outweigh the disadvantages of the connection latency.

Reference is again made to FIG. 1. Various UMTS infrastructure vendorsmove between states 122, 124, 126 and 128 based on various criteria.Exemplary infrastructures are outlined below.

In a first exemplary infrastructure, the RRC moves between an idle modeand a Cell_DCH state directly. In the Cell_DCH state, if two seconds ofinactivity are detected, the RRC state changes to a Cell_FACH state 124.If, in Cell_FACH state 124, ten seconds of inactivity are detected thenthe RRC state changes to PCH state 126. Forty five minutes of inactivityin Cell_PCH states 126 will result in the RRC state moving back to idlemode 110.

In a second exemplary infrastructure, RRC transition can occur betweenan idle mode 110 and connected mode 120 depending on a payloadthreshold. In the second infrastructure, if the payload is below acertain threshold then the UTRAN moves the RRC state to CELL_FACH state124. Conversely, if the data is above a certain payload threshold thenthe UTRAN moves the RRC state a CELL_DCH state 122. In the secondinfrastructure, if two minutes of inactivity are detected in CELL_DCHstate 122, the UTRAN moves the RRC state to CELL_FACH state 124. Afterfive minutes of inactivity in the CELL-FACH state 124, the UTRAN movesthe RRC stage to CELL_PCH state 126. In CELL_PCH state 126, two hours ofinactivity are required before moving back to idle mode 110.

In a third exemplary infrastructure, movement between idle mode andconnected mode 120 is always to CELL_DCH state 122. After five secondsof inactivity in CELL_DCH state 122 the UTRAN moves the RRC state toCELL_FACH state 124. Thirty seconds of inactivity in CELL_FACH state 124results in the movement back to idle mode 110.

In a fourth exemplary infrastructure the RRC transitions from an idlemode to a connected mode directly into a CELL_DCH state 122. In thefourth exemplary infrastructure, CELL_DCH state 122 includes twosub-states. The first includes a sub-state which has a high data rateand a second sub-state includes a lower data rate, but still within theCELL_DCH state. In the fourth exemplary infrastructure, the RRCtransitions from idle mode 110 directly into the high data rate CELL_DCHsub-state. After 10 seconds of inactivity the RRC state transitions to alow data rate CELL_DCH state. Seventeen seconds of inactivity from thelow data CELL_DCH state 122 result in the RRC state changing it to idlemode 110.

The above four exemplary infrastructure shows how various UMTSinfrastructure vendors are implementing the states. As will beappreciated by those skilled in the art, in each case, if the time spenton exchanging actual data (such as an email) is significantly shortcompared to the time that is required to stay in the CELL_DCH or theCELL_FACH states, this causes unnecessary current drain which makes userexperience in newer generation networks such as UMTS worse than in priorgeneration networks such as GPRS.

Further, although the CELL_PCH state is more optimal than the CELL_FACHstate from a battery life perspective, the DRX cycle in a CELL_PCH stateis typically set to a lower value than the idle mode 110. As a result,the UE is required to wake up more frequently in the CELL_PCH state thanin an idle mode.

The URA_PCH state with a DRX cycle similar to that of the idle state islikely the optimal trade up between battery life and latency forconnection. However, URA_PCH is currently not supported in the UTRAN. Itis therefore desirable to quickly transition to the idle mode as quicklyas possible after an application is finished with the data exchange froma battery life perspective.

Reference is now made to FIG. 3. When transitioning from an idle mode toa connected mode various signaling and data connections need to be made.Referring to FIG. 3, the first item needing to be performed is an RRCconnection set-up. As indicated above, this RRC connection setup canonly be torn down by the UTRAN.

Once RRC connection setup 310 is accomplished, a signaling connectionsetup 312 is started.

Once signaling setup 312 is finished, a ciphering and integrity setup314 is started. Upon completion of this, a radio bearer setup 316 isaccomplished. At this point, data can be exchanged between the UE andUTRAN.

Tearing down a connection is similarly accomplished in the reverseorder, in general. The radio bearer setup 316 is taken down and then theRRC connection setup 310 is taken down. At this point, the RRC movesinto idle mode 110 as illustrated in FIG. 1.

Although the current 3GPP specification does not allow the UE to releasethe RRC connection or indicate its preference for RRC state, the UE canstill indicate termination of a signaling connection for a specifiedcore network domain such as the Packet Switched (PS) domain used bypacket-switched applications. According to section 8.1.14.1 of 3GPP TS25.331; the signaling connection release indication procedure is used bythe UE to indicate to the UTRAN that one of its signaling connectionshas been released. This procedure may in turn initiate the RRCconnection release procedure.

Thus staying within the current 3GPP specifications, signalingconnection release may be initiated upon the tearing down of thesignaling connection setup 312. It is within the ability of the UE totear down signaling connection setup 312, and this in turn according tothe specification “may” initiate the RRC connection release.

As will be appreciated by those skilled in the art, if signalingconnection setup 312 is torn down, the UTRAN will also need to clean updeciphering and integrity setup 312 radio bearer setup 316 after thesignaling connection setup 312 has been torn down.

If signaling connections setup 312 is torn down, the RRC connectionsetup is typically brought down by the network for current vendorinfrastructures.

Using the above, if the UE determines that it is done with the exchangeof data, for example if a “RRC connection manager” component of the UEsoftware is provided with an indication that the exchange of data iscomplete, then the RRC connection manager may determine whether or notto tear down the signaling connection setup 312. For example, an emailapplication on the device sends an indication that it has received anacknowledgement from the push email server that the email was indeedreceived by the push server. The RRC manager can keep track of allexisting applications, associated PDP contexts, associated PS radiobearers and associated circuit switched (CS) radio bearers. A delay inthis case can be introduced to ensure that the application is trulyfinished with data exchange and no longer requires an RRC connectioneven after it has sent the “done” indication. This delay is equivalentto inactivity timeout associated with the application. Each applicationcan have its own inactivity timeout. For example, an email applicationcan have an inactivity timeout of five seconds, whereas an activebrowser application can have a timeout of sixty seconds. Based on acomposite status of all such indications from active applications, theUE software decides how long it should wait before it can initiate asignaling connection release of the appropriate core network (e.g. PSDomain).

The inactivity timeout can be made dynamic based on a traffic patternhistory and/or application profile.

Whenever the RRC connection manager determines with some probabilitythat no application is expecting the exchange of data, it can send asignaling connection release indication procedure for the appropriatedomain.

The above UE initiated transition to idle mode can happen in any stageof the RRC connected mode 120 as illustrated in FIG. 1 and ends uphaving the network release the RRC connection and moving to a idle mode110 as illustrated in FIG. 1. This is also applicable when the UE isperforming any packet data services during a voice call. In this caseonly the PS domain is released, but the CS domain remains connected.

A problem from the network perspective for the above is that thesignaling release indication sent by the UE is interpreted as an alarm.In the case where the signaling network release is a result of anexplicit action by the UE due to an application timer expiring and thusno further expectation of data, the alarm caused by the above indicationskews performance and alarm indications. Key performance indicatorsmight be altered by this, leading to a loss of efficiency.

Preferably, a cause could be added to the signaling connection releaseindication indicating to the UTRAN the reason for the indication. In apreferred embodiment, the cause could be an indication that an abnormalstate caused the indication or that the indication was initiated by theUE as a result of a requested idle transition. Other normal (i.e.non-abnormal) transactions could also result in the sending of thesignaling connection release indication.

In a further preferred embodiment, various timeouts can cause asignaling connection indication to be sent for an abnormal condition.The examples of timers below is not exhaustive, and other timers orabnormal conditions are possible. For example, 10.2.47 3GPP TS 24.008specifies timer T3310 as:

TIMER T3310 ON THE 1^(st), 2^(nd), 3^(rd), TIMER TIMER CAUSE OF 4^(th)EXPIRY NUM. VALUE STATE START NORMAL STOP Note 3 T3310 15 s GMM- ATTACHREQ sent ATTACH ACCEPT Retransmission REG- received of ATTACH INITATTACH REJECT REQ received

This timer is used to indicate an attachment failure. The failure toattach could be a result of the network or could be a radio frequency(RF) problem such as a collision or bad RF.

The attachment attempt could occur multiple times, and an attachmentfailure results from either a predetermined number of failures or anexplicit rejection.

A second timer of 10.2.47 of 3GPP is timer T3330, which is specified as:

TIMER T3330 ON THE 1^(st), 2^(nd), 3^(rd), TIMER TIMER CAUSE OF 4^(th)EXPIRY NUM. VALUE STATE START NORMAL STOP Note 3 T3330 15 s GMM- ROUTINGROUTING AREA Retransmission ROUTING- AREA UPDATE UPDATE ACC received ofthe UPDATING- REQUEST sent ROUTING AREA ROUTING INITIATED UPDATE REJreceived AREA UPDATE REQUEST message

This timer is used to indicate a routing area update failure. Uponexpiry of the timer, a further routing area update could be requestedmultiple times and a routing area update failure results from either apredetermined number of failures or an explicit rejection.

A third timer of 10.2.47 of 3GPP is timer T3340, which is specified as:

TIMER T3340 ON THE 1^(st), 2^(nd), 3^(rd), TIMER TIMER CAUSE OF 4^(th)EXPIRY NUM. VALUE STATE START NORMAL STOP Note 3 T3340 10 s GMM- ATTACHREJ, PS signalling Release the PS (Iu REG-INIT DETACH REQ, connectionreleased signalling mode GMM- ROUTING AREA connection and only)DEREG-INIT UPDATE REJ or proceed as GMM-RA- SERVICE REJ described inUPDATING- with any of the subclause INT causes #11, #12, 4.7.1.9GMM-SERV- #13 or #15. REQ-INIT (Iu ATTACH mode only) ACCEPT or GMM-ROUTING AREA ATTEMPTING- UPDATE TO- ACCEPT is UPDATE-MM received with“no GMM-REG- follow-on proceed” NORMAL- indication. SERVICE

This timer is used to indicate a GMM service request failure. Uponexpiry of the timer, a further GMM service request could be initiatedmultiple times and a GMM service request failure results from either apredetermined number of failures or an explicit rejection.

Thus, instead of a signaling release indication cause limited to anabnormal condition and a release by the UE, the signaling releaseindication cause could further include information about which timerfailed for an abnormal condition. A signaling connection releaseindication could be structured as:

SIGNALING CONNECTION RELEASE INDICATION IE type Information andSemantics Element/Group name Need Multi reference description MessageType MP Message type UE Information Elements Integrity check info CHIntegrity check info 10.3.3.16 CN information elements CN domainidentity MP CN domain identity 10.3.1.1 Signaling Release OP Signalingt3310 timeout, Indication Cause Release t3330 timeout, Indication t3340timeout, Cause UE Requested Idle Transition

This message is used by the UE to indicate to the UTRAN the release ofan existing signaling connection. The addition of the signaling releaseindication cause allows the UTRAN or other network element to receivethe cause of the signaling release indication, whether it was due to anabnormal condition, and what the abnormal condition was. And, an RRCconnection release procedure is, in turn, permitted to be initiated.

In one implementation, the UE, upon receiving a request to release, orabort, a signaling connection from upper layers for a specific CN (corenetwork) domain initiate the signaling connection release indicationprocedure if a signaling connection as identified in a variable, e.g., avariable ESTABLISHED_SIGNALING_CONNECTIONS, for the specific CN domainidentified with the IE (information element) “CN domain identity”exists. If the variable does not identify any existing signalingconnection, any ongoing establishment of signaling connection for thatspecific CN domain is aborted in another manner. And, upon initiation ofthe signaling connection release indication procedures in the Cell_PCHor URA_PCH states, the UE performs a cell update procedure using a cause“uplink data transmission”. And, when a cell update procedure iscompleted successfully, the UE continues with the signaling connectionrelease indication procedures that follow.

Namely, the UE sets the IE “CN domain identity” to the value indicatedby upper logical layers. The value of the IE indicates the CN domainwhose associated signaling connection the associated signalingconnection that the upper layers are indicating to be released. If theCN domain identity is set to the PS domain, and if the upper layerindicates the cause to initiate this request, then the IE “signalingrelease indication cause” is accordingly set. The UE further removes thesignaling connection with the identity indicated by upper layers fromthe variable “established_signaling_connections”. And, the UE transmitsa signaling connection release indication message on, e.g., the DCCHusing AM RLC. Upon confirmation of successful delivery of the releaseindication message by the RLC, the procedure ends.

An IE “Signaling Release Indication Cause is also used pursuant to anembodiment of the present disclosure. The release cause is aligned, forinstance, with existing message definitions. The upper layer releasecause message is structured, e.g., as:

Information Element/Group IE type and Semantics name Need Multireference description Signaling Release Indication MP Enumerated Cause(UE Requested PS Data session end, T3310 expiry, T3330 expiry, T3340expiry)In this example, the T3310, T330, and T3340 expiries correspond toexpiration of correspondingly-numbered timers identified previously. Acause value is settable, in one implementation, as a “UE Requested PSData session end” rather than a “UE Requested idle transition” toprovide for the UTRAN to decide upon the state transition, although theexpected result corresponds to that identified by the cause value. Theextension to the signaling connection release indication is preferably,but not necessarily, a non-critical extension.

Reference is now made to FIG. 9. FIG. 9 is a flow chart of an exemplaryUE monitoring whether or not to send a signaling connection releaseindication for various domains (e.g. PS or CS). The process starts instep 910.

The UE transitions to step 912 in which it checks to see whether anabnormal condition exists. Such an abnormal condition can include, forexample, timer T3310, timer T3320, or timer T3340 expiring as describedabove. If these timers expire a certain predetermined number of times orif an explicit rejection is received based on the expiry of any of thesetimers, the UE proceeds to step 914 in which is sends a signalingconnection release indication. The signaling connection releaseindication message is appended with a signaling release indication causefield. The signaling release indication cause field includes at leastthat the signaling release indication is based on an abnormal conditionor state and a preferred embodiment includes the specific timer thattimed out to result in the abnormal condition.

Conversely, if in steps 912 the UE finds that no abnormal conditionexists, the UE proceeds to step 920 in which it checks whether furtherdata is expected at the UE. This can, as described above, include whenan email is sent and confirmation of the sending of the email isreceived back at the UE. Other examples of where the UE will determinethat no further data is expected would be known to those skilled in theart.

If in step 920 the UE determines that the data transfer is finished (orin the case of a circuit switched domain that a call is finished) the UEproceeds to step 922 in which it sends a signaling connection releaseindication in which the signaling release indication cause field hasbeen added and includes the fact that the UE requested an idletransition.

From step 920, if the data is not finished the UE loops back andcontinues to check whether an abnormal condition exists in step 912 andwhether the data is finished in step 920.

Once the signaling connection release indication is sent in step 914 orstep 922, the process proceeds to step 930 and ends.

The UE includes functional elements, implementable, for instance, byapplications or algorithms carried out through operation of a UEmicroprocessor or by hardware implementation, that form a checker and asignaling connection release indication sender. The checker isconfigured to check whether a signaling connection release indicationshould be sent. And, a signaling connection release indication sender isconfigured to send a signaling connection release indication responsiveto indication by the checker that the signaling connection releaseindication should be sent. The signaling connection release indicationincludes a signaling release indication cause field.

In one implementation, the network is, instead, implicitly made aware oftiming out of a timer, and the UE need not send a cause value indicatingthe timing out of the timer. That is to say, the timer starts timingupon authorization of the network. Cause codes are defined, and thecause codes are provided by the network to the UE. Such cause codes areused by the UE to initiate the timer. And, the network is implicitlyaware of the reason for subsequent timing out of the timer as the causecode earlier sent bv the network causes the timer to time. And, as aresult, the UE need not send a cause value indicating the timing out ofthe timer.

Referring to FIG. 10, when a network element receives the signalingconnection release indication in step 1010 the network element examinesthe signaling release indication cause field in step 1014 and in step1016 checks whether the cause is an abnormal cause or whether it is dueto the UE requesting an idle transition. If in step 1016 the signalingconnection release indication is of abnormal cause, the network nodeproceeds to step 1020 in which an alarm is noted for performancemonitoring and alarm monitoring purposes. The key performance indicatorcan be updated appropriately.

Conversely, if in step 1016 the cause of the signaling connectionrelease indication is not a result of an abnormal condition, or in otherwords is a result of the UE requesting an idle transition, the networknode proceeds to step 1030 in which no alarm is raised and theindication can be filtered from the performance statistics, therebypreventing the performance statistics from being skewed. From step 1020or step 1030, the network node proceeds to step 1040 in which theprocess ends.

The reception and examination of the signaling release indication causefield results in initiation by the network element of an RRC connectionrelease procedure. And, the packet switched data connection ends.

As will be appreciated by those skilled in the art, step 1020 can beused to further distinguish between various alarm conditions. Forexample, a T3310 time out could be used to keep a first set ofstatistics and a T3330 time out could be used to keep a second set ofstatistics. Step 1020 can distinguish between the causes of the abnormalcondition, thereby allowing the network operator to track performancemore efficiently.

The network includes functional elements, implementable, for instance,by applications or algorithms carried out through operation of aprocessor or by hardware implementation, that form an examiner and analarm generator. The examiner is configured to examine a signalingrelease indication cause field of the signaling connection releaseindication. The examiner checks whether the signaling release indicationcause field indicates an abnormal condition. The alarm generator isconfigured selectably to generate an alarm if examination by theexaminer determines the signal release indication cause field indicatesthe abnormal condition.

In one implementation, upon reception of the signaling connectionrelease indication, the UTRAN forwards the cause that is received andrequests, from upper layers, for release of the signaling connection.The upper layers then are able to initiate the release of the signalingconnection. The IE signaling release indication cause indicates the UE'supper layer cause to trigger the RRC of the UE to send the message. Thecause is possibly the result of an abnormal upper layer procedure.Differentiation of the cause of the message is assured throughsuccessful reception of the IE.

A possible scenario includes a scenario in which, prior to confirmation,by the RLC, of successful delivery of the signaling connection releaseindication message, reestablishment of the transmitting side of the RLCentity on the signaling radio bearer RB2 occurs. In the event of such anoccurrence, the UE retransmits the signaling connection releaseindication message, e.g., on the uplink DCCH using AM RLC on signalingradio bearer RB2. In the event that an enter-RAT handover fromperformance of a UTRAN procedure occurs prior to successful delivery ofconfirmation, by the RLC, of the successful delivery of the signalingconnection release indication message, the UE aborts the signalingconnection while in the new RAT.

Referring again to FIG. 1, in some cases it may be more desirable to bein the connected mode state URA_PCH than in idle mode. For example, ifthe latency for connection to the CELL_DCH or the CELL_FACH connectedmode states is required to be lower, it is preferable to be in aconnected mode PCH state. There are two ways of accomplishing this.First is by changing the 3GPP specifications to allow for the UE torequest the UTRAN move it to a specific state, in this case the URA_PCHstate 128.

Alternatively, the RRC connection manager may take into account otherfactors such as what state the RRC connection is currently in. If, forexample, the RRC connection is in the URA_PCH state it may decide thatit is unnecessary to move to idle mode 110 and thus no Signalingconnection release procedure is initiated.

Reference is made to FIG. 4. FIG. 4A shows a current UMTS implementationaccording to the infrastructure “four” example above. As illustrated inFIG. 4, time is across the horizontal axes.

The UE starts in RRC idle state 110 and based on local data needing tobe transmitted or a page received from the UTRAN, starts to establish anRRC connection.

As illustrated in FIG. 4A, RRC connection setup 310 occurs first, andthe RRC state is a connecting state 410 during this time.

Next, signaling connections setup 312, ciphering an integrity setup 314,and radio bearer setup 316 occurs. The RRC state is CELL_DCH state 122during this. As illustrated in FIG. 4A, the time for moving from RRCidle to the time that the radio bearer is setup is approximately twoseconds in this example.

Data is next exchanged. In the example FIG. 4A this is achieved in abouttwo to four seconds and is illustrated by step 420.

After data is exchanged in step 420, no data is being exchanged exceptfor intermittent RLC signaling PDU as required and thus the radio beareris reconfigured by the network to move into a lower data rate DCH stateafter approximately ten seconds. This is illustrated in steps 422 and424.

In the lower data rate DCH state nothing is received for seventeenseconds, at which point the RRC connection is released by the network instep 428.

Once the RRC connection is initiated in step 428, the RRC state proceedsto a disconnecting state 430 for approximately forty milliseconds, afterwhich the UE is in a RRC idle state 110.

Also illustrated in FIG. 4A, the UE current consumption is illustratedfor the period in which the RRC is in CELL_DCH state 122. As seen, thecurrent consumption is approximately 200 to 300 milliamps for the entireduration of the CELL_DCH state. During disconnect and idle, about 3milliamps are utilized, assuming a DRX cycle of 1.28 seconds. However,the 35 seconds of current consumption at 200 to 300 milliamps isdraining on the battery.

Reference is now made to FIG. 4B. FIG. 4B utilizes the same exemplaryinfrastructure “four” from above, only now implementing the signallingconnection release

As illustrated in FIG. 4B, the same setup steps 310, 312, 314 and 316occur and this takes the same amount of time when moving between RRCidle state 110 and RRC CELL_DCH state 122.

Further, the RRC data PDU exchange for the exemplary email of FIG. 4A isalso done at FIG. 4B and this takes approximately two to four seconds.

The UE in the example of FIG. 4B has an application specific inactivitytimeout, which in the example of FIG. 4B is two seconds and isillustrated by step 440. After the RRC connection manager has determinedthat there is inactivity for the specific amount of time, the UEreleases the signaling connection setup in step 442 and the RRCconnection is released by the network in step 428.

As illustrated in FIG. 4B, the current consumption during the CELL_DCHstep 122 is still about 200 to 300 milliamps. However, the connectiontime is only about eight seconds. As will appreciated by those skilledin the art, the considerably shorter amount of time that the mobilestays in the cell DCH state 122 results in significant battery savingsfor an always on UE device.

Reference is now made to FIG. 5. FIG. 5 shows a second example using theinfrastructure indicated above as Infrastructure “three”. As with FIGS.4A and 4B, a connection setup occurs which takes approximately twoseconds. This requires the RRC connection setup 310, the signalingconnection setup 312, the ciphering and integrity setup 314 and theradio bearer setup 316.

During this setup, the UE moves from RRC idle mode 110 to a CELL_DCHstate 122 with a RRC state connecting step 410 in between.

As with FIG. 4A, in FIG. 5A RLC data PDU exchange occurs, and in theexample of FIG. 5A takes two to four seconds.

According to the infrastructure three, RLC signaling PDU exchangereceives no data and thus is idle for period of five seconds in step422, except for intermittent RLC signaling PDU as required, at whichpoint the radio bearer reconfigures the network to move into a CELL_FACHstate 124 from CELL_DCH state 122. This is done in step 450.

In the CELL_FACH state 124, the RLC signaling PDU exchange finds thatthere is no data except for intermittent RLC signaling PDU as requiredfor a predetermined amount of time, in this case thirty seconds, atwhich point a RRC connection release by network is performed in step428.

As seen in FIG. 5A, this moves the RRC state to idle mode 110.

As further seen in FIG. 5A, the current consumption during the DCH modeis between 200 and 300 milliamps. When moving into CELL_FACH state 124the current consumption lowers to approximately 120 to 180 milliamps.After the RRC connector is released and the RRC moves into idle mode 110the power consumption is approximately 3 milliamps.

The UTRA RRC Connected Mode state being CELL_DCH state 122 or CELL_FACHstate 124 lasts for approximately forty seconds in the example of FIG.5A.

Reference is now made to FIG. 5B. FIG. 5B illustrates the sameinfrastructure “three” as FIG. 5A with the same connection time of abouttwo seconds to get the RRC connection setup 310, signaling connectionsetup 312, ciphering integrity setup 314 and radio bearer setup 316.Further, RLC data PDU exchange 420 take approximately two to fourseconds.

As with FIG. 4B, a UE application detects a specific inactivity timeoutin step 440, at which point the Signaling connection release indicationprocedure is initiated by the UE and as a consequence the RRC connectionis released by the network in step 448.

As can be seen further in FIG. 5B, the RRC starts in a idle mode 110,moves to a CELL_DCH state 122 without proceeding into the CELL_FACHstate.

As will be seen further in FIG. 5B, current consumption is approximately200 to 300 milliamps in the time that the RRC stage is in CELL_DCH state122 which according to the example of FIG. 5 is approximate eightseconds.

Therefore, a comparison between FIGS. 4A and 4B, and FIGS. 5A and 5Bshows that a significant amount of current consumption is eliminated,thereby extending the battery life of the UE significantly. As will beappreciated by those skilled in the art, the above can further be usedin the context of current 3GPP specs.

Reference is now made to FIG. 6. FIG. 6 illustrates a protocol stack fora UMTS network.

As seen in FIG. 6, the UMTS includes a CS control plane 610, PS controlplane 611, and PS user plane 630

Within these three planes, a non-access stratum (NAS) portion 614 and anaccess stratum portion 616 exist.

NAS portion 614 in CS control plane 610 includes a call control (CC)618, supplementary services (SS) 620, and short message service (SMS)622.

NAS portion 614 in PS control plane 611 includes both mobilitymanagement (MM) and GPRS mobility management (GMM) 626. It furtherincludes SM/RABM 624 and GSMS 628.

CC 618 provides for call management signaling for circuit switchedservices. The session management portion of SM/RABM 624 provides for PDPcontext activation, deactivation and modification. SM/RABM 624 alsoprovides for quality of service negotiation.

The main function of the RABM portion of the SM/RABM 624 is to connect aPDP context to a Radio Access Bearer. Thus SM/RABM 624 is responsiblefor the setup, modification and release of radio bearers.

CS control plane 610 and PS control plane 611, in the access stratum 616sit on radio resource control (RRC) 617.

NAS portion 614 in PS user plane 630 includes an application layer 638,TCP/UDP layer 636, and PDP layer 634. PDP layer 634 can, for example,include internet protocol (IP).

Access Stratum 616, in PS user plane 630 includes packet dataconvergence protocol (PDCP) 632. PDCP 632 is designed to make the WCDMAprotocol suitable to carry TCP/IP protocol between UE and RNC (as seenin FIG. 8), and is optionally for IP traffic stream protocol headercompression and decompression.

The UMTS Radio Link Control (RLC) 640 and Medium Access Control (MAC)layers 650 form the data link sub-layers of the UMTS radio interface andreside on the RNC node and the User Equipment.

The Layer 1 (L1) UMTS layer (physical layer 650) is below the RLC/MAClayers 640 and 650. This layer is the physical layer for communications.

While the above can be implemented on a variety of mobile devices, anexample of one mobile device is outlined below with respect to FIG. 7.Reference is now made to FIG. 7.

UE 1100 is preferably a two-way wireless communication device having atleast voice and data communication capabilities. UE 1100 preferably hasthe capability to communicate with other computer systems on theInternet. Depending on the exact functionality provided, the wirelessdevice may be referred to as a data messaging device, a two-way pager, awireless e-mail device, a cellular telephone with data messagingcapabilities, a wireless Internet appliance, or a data communicationdevice, as examples.

Where UE 1100 is enabled for two-way communication, it will incorporatea communication subsystem 1111, including both a receiver 1112 and atransmitter 1114, as well as associated components such as one or more,preferably embedded or internal, antenna elements 1116 and 1118, localoscillators (LOs) 1113, and a processing module such as a digital signalprocessor (DSP) 1120. As will be apparent to those skilled in the fieldof communications, the particular design of the communication subsystem1111 will be dependent upon the communication network in which thedevice is intended to operate. For example, UE 1100 may include acommunication subsystem 1111 designed to operate within the GPRS networkor UMTS network.

Network access requirements will also vary depending upon the type ofnetwork 1119. For example, In UMTS and GPRS networks, network access isassociated with a subscriber or user of UE 1100. For example, a GPRSmobile device therefore requires a subscriber identity module (SIM) cardin order to operate on a GPRS network. In UMTS a USIM or SIM module isrequired. In CDMA a RUIM card or module is required. These will bereferred to as a UIM interface herein. Without a valid UIM interface, amobile device may not be fully functional. Local or non-networkcommunication functions, as well as legally required functions (if any)such as emergency calling, may be available, but mobile device 1100 willbe unable to carry out any other functions involving communications overthe network 1100. The UIM interface 1144 is normally similar to acard-slot into which a card can be inserted and ejected like a disketteor PCMCIA card. The UIM card can have approximately 64K of memory andhold many key configuration 1151, and other information 1153 such asidentification, and subscriber related information.

When required network registration or activation procedures have beencompleted, UE 1100 may send and receive communication signals over thenetwork 1119. Signals received by antenna 1116 through communicationnetwork 1119 are input to receiver 1112, which may perform such commonreceiver functions as signal amplification, frequency down conversion,filtering, channel selection and the like, and in the example systemshown in FIG. 7, analog to digital (A/D) conversion. A/D conversion of areceived signal allows more complex communication functions such asdemodulation and decoding to be performed in the DSP 1120. In a similarmanner, signals to be transmitted are processed, including modulationand encoding for example, by DSP 1120 and input to transmitter 1114 fordigital to analog conversion, frequency up conversion, filtering,amplification and transmission over the communication network 1119 viaantenna 1118. DSP 1120 not only processes communication signals, butalso provides for receiver and transmitter control. For example, thegains applied to communication signals in receiver 1112 and transmitter1114 may be adaptively controlled through automatic gain controlalgorithms implemented in DSP 1120.

Network 1119 may further communicate with multiple systems, including aserver 1160 and other elements (not shown). For example, network 1119may communicate with both an enterprise system and a web client systemin order to accommodate various clients with various service levels.

UE 1100 preferably includes a microprocessor 1138 which controls theoverall operation of the device. Communication functions, including atleast data communications, are performed through communication subsystem1111. Microprocessor 1138 also interacts with further device subsystemssuch as the display 1122, flash memory 1124, random access memory (RAM)1126, auxiliary input/output (I/O) subsystems 1128, serial port 1130,keyboard 1132, speaker 1134, microphone 1136, a short-rangecommunications subsystem 1140 and any other device subsystems generallydesignated as 1142.

Some of the subsystems shown in FIG. 7 perform communication-relatedfunctions, whereas other subsystems may provide “resident” or on-devicefunctions. Notably, some subsystems, such as keyboard 1132 and display1122, for example, may be used for both communication-related functions,such as entering a text message for transmission over a communicationnetwork, and device-resident functions such as a calculator or tasklist.

Operating system software used by the microprocessor 1138 is preferablystored in a persistent store such as flash memory 1124, which mayinstead be a read-only memory (ROM) or similar storage element (notshown). Those skilled in the art will appreciate that the operatingsystem, specific device applications, or parts thereof, may betemporarily loaded into a volatile memory such as RAM 1126. Receivedcommunication signals may also be stored in RAM 1126. Further, a uniqueidentifier is also preferably stored in read-only memory.

As shown, flash memory 1124 can be segregated into different areas forboth computer programs 1158 and program data storage 1150, 1152, 1154and 1156. These different storage types indicate that each program canallocate a portion of flash memory 1124 for their own data storagerequirements. Microprocessor 1138, in addition to its operating systemfunctions, preferably enables execution of software applications on themobile device. A predetermined set of applications that control basicoperations, including at least data and voice communication applicationsfor example, will normally be installed on UE 1100 during manufacturing.A preferred software application may be a personal information manager(PIM) application having the ability to organize and manage data itemsrelating to the user of the mobile device such as, but not limited to,e-mail, calendar events, voice mails, appointments, and task items.Naturally, one or more memory stores would be available on the mobiledevice to facilitate storage of PIM data items. Such PIM applicationwould preferably have the ability to send and receive data items, viathe wireless network 1119. In a preferred embodiment, the PIM data itemsare seamlessly integrated, synchronized and updated, via the wirelessnetwork 1119, with the mobile device user's corresponding data itemsstored or associated with a host computer system. Further applicationsmay also be loaded onto the mobile device 1100 through the network 1119,an auxiliary I/O subsystem 1128, serial port 1130, short-rangecommunications subsystem 1140 or any other suitable subsystem 1142, andinstalled by a user in the RAM 1126 or preferably a non-volatile store(not shown) for execution by the microprocessor 1138. Such flexibilityin application installation increases the functionality of the deviceand may provide enhanced on-device functions, communication-relatedfunctions, or both. For example, secure communication applications mayenable electronic commerce functions and other such financialtransactions to be performed using the UE 1100. These applications willhowever, according to the above, in many cases need to be approved by acarrier.

In a data communication mode, a received signal such as a text messageor web page download will be processed by the communication subsystem1111 and input to the microprocessor 1138, which preferably furtherprocesses the received signal for output to the display 1122, oralternatively to an auxiliary I/O device 1128. A user of UE 1100 mayalso compose data items such as email messages for example, using thekeyboard 1132, which is preferably a complete alphanumeric keyboard ortelephone-type keypad, in conjunction with the display 1122 and possiblyan auxiliary I/O device 1128. Such composed items may then betransmitted over a communication network through the communicationsubsystem 1111.

For voice communications, overall operation of UE 1100 is similar,except that received signals would preferably be output to a speaker1134 and signals for transmission would be generated by a microphone1136. Alternative voice or audio I/O subsystems, such as a voice messagerecording subsystem, may also be implemented on UE 1100. Although voiceor audio signal output is preferably accomplished primarily through thespeaker 1134, display 1122 may also be used to provide an indication ofthe identity of a calling party, the duration of a voice call, or othervoice call related information for example.

Serial port 1130 in FIG. 7 would normally be implemented in a personaldigital assistant (PDA)-type mobile device for which synchronizationwith a user's desktop computer (not shown) may be desirable. Such a port1130 would enable a user to set preferences through an external deviceor software application and would extend the capabilities of mobiledevice 1100 by providing for information or software downloads to UE1100 other than through a wireless communication network. The alternatedownload path may for example be used to load an encryption key onto thedevice through a direct and thus reliable and trusted connection tothereby enable secure device communication.

Alternatively, serial port 1130 could be used for other communications,and could include as a universal serial bus (USB) port. An interface isassociated with serial port 1130.

Other communications subsystems 1140, such as a short-rangecommunications subsystem, is a further optional component which mayprovide for communication between UE 1100 and different systems ordevices, which need not necessarily be similar devices. For example, thesubsystem 1140 may include an infrared device and associated circuitsand components or a Bluetooth™ communication module to provide forcommunication with similarly enabled systems and devices.

Reference is now made to FIG. 8. FIG. 8 is a block diagram of acommunication system 800 which includes a UE 802 which communicatesthrough a wireless communication network.

UE 802 communicates wirelessly with one of multiple Node Bs 806. EachNode B 806 is responsible for air interface processing and some radioresource management functions. Node B 806 provides functionality similarto a Base Transceiver Station in a GSM/GPRS networks.

The wireless link shown in communication system 800 of FIG. 8 representsone or more different channels, typically different radio frequency (RF)channels, and associated protocols used between the wireless network andUE 802. A Uu air interface 804 is used between UE 802 and Node B 806.

An RF channel is a limited resource that must be conserved, typicallydue to limits in overall bandwidth and a limited battery power of UE802. Those skilled in art will appreciate that a wireless network inactual practice may include hundreds of cells depending upon desiredoverall expanse of network coverage. All pertinent components may beconnected by multiple switches and routers (not shown), controlled bymultiple network controllers.

Each Node B 806 communicates with a radio network controller (RNC) 810.The RNC 810 is responsible for control of the radio resources in itsarea. One RNC 810 control multiple Node Bs 806.

The RNC 810 in UMTS networks provides functions equivalent to the BaseStation Controller (BSC) functions in GSM/GPRS networks. However, an RNC810 includes more intelligence including, for example, autonomoushandovers management without involving MSCs and SGSNs.

The interface used between Node B 806 and RNC 810 is an Iub interface808. An NBAP (Node B application part) signaling protocol is primarilyused, as defined in 3GPP TS 25.433 V3.11.0 (2002-09) and 3GPP TS 25.433V5.7.0 (2004-01).

Universal Terrestrial Radio Access Network (UTRAN) 820 comprises the RNC810, Node B 806 and the Uu air interface 804.

Circuit switched traffic is routed to Mobile Switching Centre (MSC) 830.MSC 830 is the computer that places the calls, and takes and receivesdata from the subscriber or from PSTN (not shown).

Traffic between RNC 810 and MSC 830 uses the Iu-CS interface 828. Iu-CSinterface 828 is the circuit-switched connection for carrying(typically) voice traffic and signaling between UTRAN 820 and the corevoice network. The main signaling protocol used is RANAP (Radio AccessNetwork Application Part). The RANAP protocol is used in UMTS signalingbetween the Core Network 821, which can be a MSC 830 or SSGN 850(defined in more detail below) and UTRAN 820. RANAP protocol is definedin 3GPP TS 25.413 V3.11.1 (2002-09) and TS 25.413 V5.7.0 (2004-01).

For all UEs 802 registered with a network operator, permanent data (suchas UE 102 user's profile) as well as temporary data (such as UE's 802current location) are stored in a home location registry (HLR) 838. Incase of a voice call to UE 802, HLR 838 is queried to determine thecurrent location of UE 802. A Visitor Location Register (VLR) 836 of MSC830 is responsible for a group of location areas and stores the data ofthose mobile stations that are currently in its area of responsibility.This includes parts of the permanent mobile station data that have beentransmitted from HLR 838 to the VLR 836 for faster access. However, theVLR 836 of MSC 830 may also assign and store local data, such astemporary identifications. UE 802 is also authenticated on system accessby HLR 838.

Packet data is routed through Service GPRS Support Node (SGSN) 850. SGSN850 is the gateway between the RNC and the core network in a GPRS/UMTSnetwork and is responsible for the delivery of data packets from and tothe UEs within its geographical service area. Iu-PS interface 848 isused between the RNC 810 and SGSN 850, and is the packet-switchedconnection for carrying (typically) data traffic and signaling betweenthe UTRAN 820 and the core data network. The main signaling protocolused is RANAP (described above).

The SSGN 850 communicates with the Gateway GPRS Support Node (GGSN) 860.GGSN 860 is the interface between the UMTS/GPRS network and othernetworks such as the Internet or private networks. GGSN 860 is connectedto a public data network PDN 870 over a Gi interface.

Those skilled in art will appreciate that wireless network may beconnected to other systems, possibly including other networks, notexplicitly shown in FIG. 8. A network will normally be transmitting atvery least some sort of paging and system information on an ongoingbasis, even if there is no actual packet data exchanged. Although thenetwork consists of many parts, these parts all work together to resultin certain behaviours at the wireless link.

The embodiments described herein are examples of structures, systems ormethods having elements corresponding to elements of the techniques ofthis application. This written description may enable those skilled inthe art to make and use embodiments having alternative elements thatlikewise correspond to the elements of the techniques of thisapplication. The intended scope of the techniques of this applicationthus includes other structures, systems or methods that do not differfrom the techniques of this application as described herein, and furtherincludes other structures, systems or methods with insubstantialdifferences from the techniques of this application as described herein.

1. A method for processing signaling release indication cause betweenuser equipment and a wireless network, comprising the steps of: a.monitoring, at the user equipment, whether a signaling connectionrelease indication should be sent to the wireless network; b. appending,at the user equipment, a cause for the signaling connection releaseindication to the signaling connection release indication; c. sendingthe appended signaling connection release indication to the wirelessnetwork; d. receiving the signaling connection release indication at thewireless network; and e. filtering said cause to determine whether toraise an alarm.
 2. The method of claim 1, wherein the cause is anabnormal condition.
 3. The method of claim 2, wherein the abnormalcondition is the expiry of a timer.
 4. The method of claim 3, whereinthe timer is selected from the group consisting of a attachment failuretimer, a routing area update timer and a GMM service request timer. 5.The method of claim 1, wherein the cause is a request by the userequipment to end PS data session and thereby transition to an idle mode.6. The method of claim 1, wherein the filtering step raises an alarmwhen said cause is an abnormal condition.
 7. The method of claim 1,wherein the filtering step ignores the signaling connection releaseindication when said cause is an idle transition request by the userequipment.
 8. A system adapted for processing signaling releaseindication cause, the system comprising: a. user equipment, the userequipment having a radio subsystem including a radio adapted tocommunicate with a network; a radio processor having a digital signalprocessor and adapted to interact with said radio subsystem; memory; auser interface; a processor adapted to run user applications andinteract with the memory, the radio and the user interface and adaptedto run applications, the user equipment characterized by having meansfor: i. monitoring whether a signaling connection release indicationshould be sent to the wireless network; ii. appending a cause for thesignaling connection release indication to the signaling connectionrelease indication; and iii. sending the appended signaling connectionrelease indication to the wireless network; and b. a wireless networkadapted to communicate with the user equipment and further characterizedby means for: i. receiving the signaling connection release indication;and ii. filtering said cause to determine whether to raise an alarm. 9.The system of claim 8, wherein the cause is an abnormal condition. 10.The system of claim 9, wherein the abnormal condition is the expiry of atimer.
 11. The system of claim 10, wherein the timer is selected fromthe group consisting of a attachment failure timer, a routing areaupdate timer and a GMM service request timer.
 12. The system of claim11, wherein the cause is a request by the user equipment to end PS datasession and transition to an idle mode.
 13. The system of claim 8,wherein the means for filtering is adapted to raise an alarm when saidcause is an abnormal condition.
 14. The system of claim 8, wherein themeans for filtering is adapted to ignore the signaling connectionrelease indication when said cause is an idle transition request by theuser equipment.
 15. A method for processing signaling release indicationcause at user equipment for improved alarm tracking at a wirelessnetwork, comprising the steps of: a. monitoring whether a signalingconnection release indication should be sent to the wireless network; b.appending a cause for the signaling connection release indication to thesignaling connection release indication; and c. sending the appendedsignaling connection release indication to which the cause is appended,thereby to request the signaling connection release that identifies thecause of the signaling connection release indication.
 16. The method ofclaim 15, wherein the cause is an abnormal condition.
 17. The method ofclaim 16, wherein the abnormal condition is the expiry of a timer. 18.The method of claim 17, wherein the timer is selected from the groupconsisting of a attachment failure timer, a routing area update timerand a GMM service request timer.
 19. The method of claim 15, wherein thecause is a request by the user equipment to end PS data session andtransition to an idle mode.
 20. A user equipment adapted for providingsignaling release indication cause in a network, the user equipmenthaving a radio subsystem including a radio adapted to communicate withthe network; a radio processor having a digital signal processor andadapted to interact with said radio subsystem; memory; a user interface;a processor adapted to run user applications and interact with thememory, the radio and the user interface and adapted to runapplications, the user equipment characterized by having means for: a.monitoring whether a signaling connection release indication should besent to the wireless network; b. appending a cause for the signalingconnection release indication to the signaling connection releaseindication; and c. sending the appended signaling connection releaseindication that includes the cause, thereby to identify the cause of thesignaling connection release indication along with the signalingconnection release indication.
 21. Apparatus for user equipment tofacilitate release of signaling connection, said apparatus comprising:a. a checker configured to check whether a signaling connection releaseindication connection should be sent; and b. a signaling connectionrelease indication sender configured to send a signaling connectionrelease indication responsive to indication by said checker that thesignaling connection release indication should be sent, the signalingconnection release indication including a signaling release indicationincluding a signaling release indication cause field.
 22. The apparatusof claim 21 wherein said checker is further configured to check whether,subsequent to sending of the signaling connection release indication andprior to confirmation of delivery of the signaling connection releaseindication, signaling connection of the user equipment is needed. 23.The apparatus of claim 22 wherein said signaling connection releaseindication sender is further configured to retransmit the signalingconnection release indication.
 24. Network apparatus for operating upona signaling connection release indication, said network apparatuscomprising: a. an examiner configured to examine a signaling releaseindication cause field of the signaling connection release indication tocheck whether the signaling release indication cause field indicates anabnormal condition; and b. an alarm generator configured selectably togenerate an alarm if examination by said examiner determines thesignaling release indication cause field indicates the abnormalcondition.
 25. The network apparatus of claim 24 wherein the networkapparatus includes logical layers, wherein said examiner is embodied ata first of the logical layers, said examiner further configured torequest, to a second of the logical layers, signaling connectionrelease.